-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
additional magnum importer plugins in python build dependencies #2105
Conversation
src/cmake/dependencies.cmake
Outdated
@@ -357,7 +357,6 @@ if(NOT USE_SYSTEM_MAGNUM) | |||
MagnumPlugins::AssimpImporter | |||
MagnumPlugins::BasisImporter | |||
MagnumPlugins::GltfImporter | |||
MagnumPlugins::StanfordImporter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove StanfordImporter as it doesn't support ASCII ply.
Ah, that's one of my TODOs. I'm not interested in implementing parsing of ASCII PLY files myself, but it could delegate to Assimp for those.
Where do these come from, btw? Is there some Habitat code that writes them? Might be a candidate for refactor / replacement with builtin Magnum PLY export functionality.
What StanfordImporter
can do and Assimp can't is import of files with per-vertex semantic IDs. I remember that used to be used quite often, not sure if that's still relevant for current datasets.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the thoughts on this topic.
I don't think semantic ids in .ply are necessary for python import, but ASCII ply is an easy format for hand-edited or human-readable mesh data. Agreed we generally don't try to use these in practice.
Motivation and Context
Python importer used in Habitat-lab requires linked Magnum plugins from Habitat=sim.
How Has This Been Tested
NA
Types of changes
Checklist